Method and system for modeling of system content for businesses

ABSTRACT

A method and system of managing content at a network site can allow easier use by business users. A higher level of abstraction can be used to allow business users to create their own objects that may reference or contain other objects or records as managed by a content management system. Business users do not have to learn programming code in order to work those objects, which are content types. A graphical user interface (“GUI”) can be used to help the business users to create, modify, and delete content types. The GUI and the ability for business users to the create content types greatly shortens the time between receiving software to operate a network site and launching content at that network site.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.10/434,936 entitled “Method and System for Modeling of System Contentfor Businesses” by Tulkoff et al. filed May 9, 2003 now U.S. Pat. No.7,415,484 which was related to U.S. patent application Ser. No.10/434,935 entitled “Method and System for Deployment of Content UsingCompound Objects” by Scheevel et al. filed May 9, 2003, which isassigned to the current assignee hereof and incorporated herein byreference.

FIELD OF THE INVENTION

This invention relates in general to methods and systems for managingcontent, and more particularly, to methods and systems of managingcontent at a network site to allow content types to be defined andmodified in a manner that reflects the way a business uses and thinksabout its content.

DESCRIPTION OF THE RELATED ART

Content management at web sites is becoming increasingly complicated asmore content is used at those web sites. Companies are finding thatmanaging the content is proving to be a daunting task. The organizationof content and information is constantly changing. Within an older website, all information for a content object may be self contained (doesnot reference another content object). A problem is that the contentmanagement systems used for those older sites do not understand therelationships among the content items, and consequently, provideeffectively no help whatsoever in managing those relationships.

In the past, an object type called a “record” was an example of thisgeneric content object at the tuple granularity. A record may include(1) a reference to a tuple (row) within a table of a database and (2)metadata (e.g., state information). Companies creating web sites usingthese records have typically found that they are very limited in reallife. Complex relationships may occur between data, and there is nopractical way to manage all the rows that may get returned for arelationship. For example, an article may contain a reference toauthors. However, the authors may span across many rows within one ormore databases.

Users of content management software at a business may also find thesoftware to be “user hostile” (i.e., not user friendly). The coding fortypes of objects may include references to persistent storage media.Database schemas (each database may have a different schema), tables,rows, file addresses, or other information for obtaining informationneeded to the published at a web sites would need to be known. Anemployee of the business may need extensive training in programming andknow where and how to retrieve information needed to create effectivelyclasses from which others may instantiate objects. The business'sability to launch content may be limited or delayed because thatemployee (with programming and information retrieval knowledge) isperforming too many tasks because most other employees working with thecontent would be unable to perform such tasks. Alternatively, thebusiness may hire many of such employees but only at great expense.Further, the training of such employees may have emphasized tailoringinformation for the systems, rather than for the people, that have todeal with that information.

A need exist to allow an enterprise to manage content according to thedomain's own vocabulary. A further need exists to allow business users amore active role in defining content attributes and requirements withoutneeding to know a programming language or database administration.

SUMMARY OF THE INVENTION

A method and system of managing content at a network site can alloweasier use by business users. A higher level of abstraction can be usedto allow business users to create their own objects that may referenceor contain other objects or records as managed by a content managementsystem. Business users do not have to learn programming code in order towork those objects, which are content types. A graphical user interface(“GUI”) can be used to help the business users to create, modify, anddelete the content types. The GUI and the ability for business users tocreate content types greatly shorten the time between receiving softwareto operate a network site and launching content at that network site.

In one set of embodiments, a method of managing content at a networksite can comprise generating a content type and instantiating a dataobject from the content type. The generation of the content type can beperformed via an application programming interface. The applicationprogramming interface can provide access to an application serviceslayer that overlies a content management system.

In another set of embodiments, a data processing system readable mediumcan having code embodied therein. The code can comprise an instructionfor reading information for a content type and an instruction forgenerating a structured definition of the content type using theinformation.

In still other sets of embodiments, a system for modeling content cancomprise a content management layer and an application services layerover the content management layer. The system can further comprise anapplication programming interface to the application services layer. Theapplication programming interface may be configured to allow a user tosend a content type to the content management layer via the applicationprogramming interface and application services layer.

The foregoing general description and the following detailed descriptionare exemplary and explanatory only and are not restrictive of theinvention, as defined in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the accompanying figures.

FIG. 1 includes an illustration of a hardware configuration of a networkfor managing content at a network site in accordance with a specific,non-limiting embodiment of the present invention.

FIG. 2 includes an illustration of a data processing system storagemedium including software code having instructions in accordance with anembodiment of the present invention.

FIG. 3 includes an illustration of a logical layer depiction of anetwork site.

FIG. 4 includes a process flow diagram of a method of using managingcontent at a network site in accordance with an embodiment of thepresent invention.

FIGS. 5-10 include illustrations of windows of a graphical userinterface when creating a content type.

FIGS. 11-17 include illustrations of windows of a graphical userinterface when instantiating and developing business data objects.

Skilled artisans appreciate that elements in the figures are illustratedfor simplicity and clarity and have not necessarily been drawn to scale.For example, the dimensions of some of the elements in the figures maybe exaggerated relative to other elements to help to improveunderstanding of embodiments of the present invention.

DETAILED DESCRIPTION

Reference is now made in detail to the exemplary embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts (elements).

Method and systems can be used to generate content types at a relativelyhigher level of the abstraction compared to conventional methods andsystems used for creating templates. An application programminginterface (“API”) may be used with an application services layer thatoverlies a content management system (“CMS”). A graphical user interface(“GUI”) can be a web-based content type generating tool that is coupledto the API. The GUI can allow users, who may have little, if any,computer programming knowledge, to generate, modify, and delete contenttypes. The content types may use the vocabulary and business rules usedby a particular enterprise with which the users work. Business dataobjects may be instantiated from the content types. In one embodiment,the content types may include attributes, a workflow, access controls,and potentially other information. The content types may be based on areferenced model or a containment model as will be described later inthis specification.

A business user can quickly generate and use content types much fasterthan conventional templates. For example, programmers would writecontent management applications for the templates. The programmers needto know Java or another programming language. Unlike templates, thecontent types may specify workflow and access controls for business dataobjects instantiated from the content types. The workflow allowsbusiness data objects to be processed according to the defined workflow.Access controls may be used to allow the proper access for thosespecified in or monitoring the workflow. The ability for business usersto generate, modify, and delete content types using the GUIsignificantly shortens the time between receiving content managementsoftware to operate a network site and launching content at that networksite. Such a method and system provides a truly “out-of-the-box”solution to content management.

A few terms are defined or clarified to aid in understanding thedescriptions that follow. A network includes an interconnected set ofserver and client computers over a publicly available medium (e.g., theInternet) or over an internal (company-owned) system. A user at a clientcomputer may gain access to the network using a network access provider.An Internet Service Provider (“ISP”) is a common type of network accessprovider.

The term “business content type” is intended to mean a content typedefined in terms of a user's business context.

The term “business data object” is intended to mean an instantiation ofa business content type. Business data objects may be instantiated bycontent contributors, who may be business users.

The term “business user” is intended to mean a person having little, ifany, training in computer programming and writing code in a programminglanguage.

The term “channel” is intended to mean a hierarchical navigation ofcontent on a site. A channel can also be used to display content inapplications.

The term “content type” is intended to mean a structured definition ofan object used to instantiate other objects. The definition may compriseattributes and related data, including workflow, security, status, orother information. The content types can be used for instantiatingbusiness data objects.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a method,process, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such method, process,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

Before discussing embodiments of the present invention, an exemplaryhardware architecture for using embodiments of the present invention isdescribed. FIG. 1 illustrates an exemplary architecture and includes CMS120, content delivery system (“CDS”) 140, and actor computer 160 eachbidirectionally coupled to internal network 11.

Each of CMS 120 and CDS 140 is a server computer and is bidirectionallycoupled to a corresponding database 12 and 14, respectively. Each ofdatabases 12 and 14 may contain objects and metadata regarding thoseobjects in tables within those databases. A database server (not shown)may lie between any one or more of the databases 12 and 14 and theserver computers 120 and 140. More or fewer databases may be used, and asingle database may be shared by more than one of server computers 120and 140. For simplicity, the database server can be considered part of adatabase.

Actor computer 160 is a client computer as the term is used inclient-server relationships. Actor computer 160 can include a desktopcomputer, a laptop computer, a work station, a personal digitalassistant, a cellular phone, or nearly other device capable ofcommunicating over network 11. Other actor computers (not shown) mayalso be bidirectionally coupled to internal network 11. Individualsusing the actor computers may include content developers, editors,content reviewers, webmasters, information technology specialists, andthe like. Many of the actors are business users.

Within each of CMS 120 and CDS 140, a plurality of computers (not shown)may be interconnected to each other over internal network 11 or acombination of internal and external networks. For simplicity, a singlesystem is shown for each of CMS 120 and CDS 140. Other systems (e.g.,page generator, etc.) may be part of CMS 120 and CDS 140, or additionalsystems that are bi-directionally coupled to internal network 11.

Although not shown, a visitor computer, which is a client computer, maybe bidirectionally coupled to the CDS 140 via an external network (e.g.,the Internet). Note that FIG. 1 is a simplification of a hardwareconfiguration. Many other alternative hardware configurations arepossible and known to skilled artisans.

The CMS 120 can include central processing unit (“CPU”) 122, read-onlymemory (“ROM”) 124, random access memory (“RAM”) 126, hard drive (“HD”)or storage memory 128, and input/output device(s) (“I/O”) 129. I/O 129can include a keyboard, monitor, printer, electronic pointing device(e.g., mouse, trackball, etc.), or the like. CDS 140 can include aserver computer comprising CPU 142, ROM 144, RAM 146, HD 148, and I/O149. CDS 140 may have one or more content delivery software components,a page generator software component, a content management softwarecomponent, an applications software component, and the like. Actorcomputer 160 can comprise a CPU 162, ROM 164, RAM 166, HD 168, and I/O169.

Each of the computers in FIG. 1 may have more than one CPU, ROM, RAM,HD, I/O, or other hardware components. For simplicity, each computer isillustrated as having one of each of the hardware components, even ifmore than one is used. The content, typically in the form of objects anddatabase records, and its metadata, if any, may be located within any orall of CMS 120, CDS 140, and databases 12 and 14.

Each of computers 120, 140, and 160 is an example of a data processingsystem. ROM 124, 144, and 164; RAM 126, 146, and 166; HD 128, 148, and168; and databases 12 and 14 can include media that can be read by CPU122, 142, or 162. Therefore, each of these types of memories includes adata processing system readable medium. These memories may be internalor external to computers 120, 140, or 160.

Portions of the methods described herein may be implemented in suitablesoftware code that may reside within ROM 124, 144, or 164; RAM 126, 146,or 166; or HD 128, 148, or 168. The instructions in an embodiment of thepresent invention may be contained on a data storage device, such as HD128. FIG. 2 illustrates a combination of software code elements 204,206, and 208 that are embodied within data processing system readablemedium 202 on HD 128. Alternatively, the instructions may be stored assoftware code elements on a DASD array, magnetic tape, floppy diskette,optical storage device, or other appropriate data processing systemreadable medium or storage device.

In an illustrative embodiment of the invention, the computer-executableinstructions may be lines of compiled C⁺⁺, Java, or other language code.Other architectures may be used. For example, the functions of any oneof the computers may be performed by a different computer shown inFIG. 1. Additionally, a computer program or its software components withsuch code may be embodied in more than one data processing systemreadable medium in more than one computer.

In the hardware configuration above, the various software components(e.g., content delivery, page generator, content management, or thelike) may reside on a single server computer or on any combination ofseparate server computers. In alternative embodiments, some or all ofthe software components may reside on the same server computer. Forexample, the content delivery software component and the page generatorsoftware component could reside on the same server computer.

Communications between any of the computers in FIG. 1 can beaccomplished using electronic, optical, radio-frequency, or othersignals. For example, when a user is at actor computer 180, actorcomputer 180 may convert the signals to a human understandable form whensending a communication to the user and may convert input from a humanto appropriate electronic, optical, radio-frequency, or other signals tobe used by, systems 120 or 140. Similarly, when an operator is at CMS120, its server computer may convert the signals to a humanunderstandable form when sending a communication to the operator and mayconvert input from a human to appropriate electronic, optical,radio-frequency, or other signals to be used by actor computer 160 orsystems 120 or 140.

Attention is now directed to descriptions of managing content at anetwork site. Business content types can be created by business userswithout an extensive knowledge of a programming language. The businesscontent types can be defined in terms that are easier to understand bythe business users without affecting how the data are handled by CMS120.

In one embodiment, different levels of abstraction can be used toseparate the management of data within persistent data sources fromcontent types used in instantiating business data objects, where thebusiness data objects may use the data within the persistent datasources. FIG. 3 includes an illustration of different logical layers forcontent and its management. Persistence layer 320 can include allobjects, records, metadata for the objects and records, and other data(collectively “data”) used at the network site. The data can reside in avariety of persistent data sources. The data may be located withindifferent persistent data sources include databases, unstructuredcontent (e.g., text files, image files, etc.), structured content (e.g.,XML documents), integration sources (e.g., Enterprise Resource Planning(“ERP”), Customer Relationship Management (“CRM”), SoftwareConfiguration Management (“SCM”), etc.), other content repositories, andthird party aggregation sources (e.g., news wire services, etc.).

Content management system (“CMS”) 340 can control data withinpersistence layer 320 that are used at the network site. Applicationservices layer 360 overlies CMS 340 and provides an interface to CMS 340that allows operations to be performed on data within persistence layer320. API 380 overlies application services layer 360. Other APIs toapplication services layer 360 may be present but are not shown in FIG.3.

The interfaces from application services layer 360 (to GUI 390) and CMS340 (to application services layer 360) may be generic. With such aconfiguration, other user interfaces (not shown) to API 380 may be addedwith little additional complexity. Also, other software components (notshown) above CMS 340 and at the same level as application services layer360 may be easily added.

GUI 390 can be coupled to API 380 and allows business users to generate,modify, and delete higher-level objects (i.e., objects that reference orcontain other data within persistence layer 320) in a manner consistentwith how an enterprise thinks about its content. Because the contenttypes are objects that reside at a higher level compared to records andobjects at leaf nodes (i.e., objects that do not refer to otherobjects), GUI 390 can allow business users to generate, modify, ordelete content types without having to know a programming language. GUI390 can be a user friendly, web-based modeling tool that may be usedafter a little training, and in some cases, less than an hour oftraining. The time from installation of the methods and system describedherein to launch of content can be performed much quicker and at afraction of the cost (since programmers are not required and time togenerate the content types is faster than coding even if the programmerswere to generate the content types). The content types essentiallyreplace conventional templates that required programmers to code.Further, unlike conventional templates, the content types may have anassociated workflow and access controls to allow for a more automateddevelopment, processing, deployment of content, and a role-basedmonitoring system for monitoring the business data objects instantiatedfrom the business content types.

GUI 390 may allow business users at actor computer 160 to definebusiness content types in terms of the business's needs and in thebusiness's own vocabulary. The business content type, which is an objecttype, can comprise an XML document of a structured definition of thecontent type. A business user can model the content type based on thecontent structure desired by the business user. The business user mayspecify business rules that a business data object created from thecontent type will need to follow, who has what access to business dataobjects.

GUI 390 may present a business user at actor computer 160 with one ormore entry forms. Each attribute in the entry form can include aconfigurable control with an eXtensible Style Language Transformation(“XSLT”). GUI 390 may allow the content types to model complex databaserelationships, such as one to one (employee/image of employee), one tomany (product category/SKUs for products within the product category),and many to many (articles/authors).

The business content type may have its dependencies managed bycontainment, reference, or a combination of them. For containment, alldata for a business data object can be created, updated, deleted,versioned, associated, staged (put through a workflow), and published(deployed) as a single entity. As an example, a business content typemay contain several different records that are parts of differentdatabases. For reference, all objects referenced within a business dataobject (instantiated from the content type) may or may not be processedtogether. If a referenced object has already been deployed, it may notbe re-deployed when the business data object referencing it is deployed.

GUI 390 can be configured to include many extensibility points. Forinstance, an XML Schema Definition (“XSD”) can be added. XSD can be astructured definition for a valid XML document in lieu of a DocumentType Definition (“DTD”). XSD allows a user to define complex data typesfor the document. The content type can be generated so that it overridesa content management applications presentation for a Java Server Page(“JSP”). Custom controls may be added to allow data selection from otherdata sources. A default workflow process can be associated with eachcontent type.

Attention is now directed to FIG. 4 that includes an exemplary processflow for managing content at a network site. The method can comprisestoring data within the persistence layer (block 402), generating ormodifying a business content type (block 422), instantiating a businessdata object using the business content type (block 442), processing thebusiness data object using a workflow (block 444), and deleting thebusiness data object (block 446). Each operation will be explained belowin more detail.

Note that not all the activities described in the process flow diagramare required, that an element within a specific activity may not berequired, and that further activities may be performed in addition tothose illustrated. After reading this specification, skilled artisanswill be capable of determining what activities can be used for theirspecific needs.

Attention is now directed to details of managing content at a networksite. Referring to FIG. 4, the method can comprise storing data withinpersistence layer 320 (block 402). The data may originate within thebusiness managing the network site or may come from a third party. Thedata comprises the information that will form the content delivered bythe network site. The data can comprise other information that is notpublished at the network site (e.g., the enterprise's internal records).Databases and their schemas and repositories with files and other dataare typically designed to work best with the particular hardware andsoftware configuration of the network site. Referring to FIG. 1, thedata should be stored in a manner in which CMS 120 and CDS 140 can workquickly, efficiently, and without any significant errors. Therefore,names and locations of data within persistence layer 320 may be dictatedby hardware and software considerations and may not be user friendly oreven make sense to business users. In one embodiment, content andmetadata regarding that content may be stored in different persistentdata sources.

The method can also comprise generating or modifying a business contenttype (block 422). The business content type may be generated or modifiedusing GUI 390 as will be described with respect to window views later inthis specification. During generation or modification of the businesscontent types, a business user at actor computer 180 can use GUI 390 tocreate or edit attributes. For example, an article content type caninclude attributes, such as a title, a byline, an image, text, and thelike.

During the generation or modification of the business content type, thebusiness user may also specify workflow, security, status, orpotentially other information. The workflow may define business rules tobe followed when a business data object is instantiated from thebusiness content type. The workflow may designate who may create thebusiness data object, who may be editors and approvers, and potentiallywhen and how to publish or deploy the content corresponding to thebusiness data object. Security can be used to designate accessprivileges for activities, such as create, modify, read-only, delete,and the like. When the information for the business content type hasbeen input, the business content type may be automatically saved by CMS120 as a structured definition of the content type in XML.

After the business content type has been generated or modified, themethod can further comprise instantiating a business data object usingthe business content type (block 442). Using the article example, thebusiness data object may include an article data object instantiatedfrom the article type content type. The article identifier may beautomatically generated. GUI 390 may allow a content contributor toinput a title, an author, an image, and text. The author information mayinclude an identifier that is an author business data object backed bydata in an author information database. The business data object canreference an image file that includes an image related to the subjectmatter of the article or a photograph of the author. The image may bepersisted in a different persistent data source compared to the authorinformation (file source versus database).

The method can comprise processing the business data object using aworkflow (block 444). The workflow can define business rules for thebusiness data object from the time it is developed to the time it ispublished. Each stage of the workflow may have policies to be followedwhen performing a specific action, such as development, editing,publishing, and the like.

If the data is ever obsolete, the business data object may be deleted.The method can further comprise deleting the business data object (block446 in FIG. 4). When the business data object is deleted, the data is nolonger accessible at the network site. The examples below are used toillustrate how GUI 390 is used for generating or modifying contenttypes, instantiating business data objects, and tracking tasks. Morethan one GUI may be used for the different functions (defining contenttypes versus instantiating business data objects versus monitoringstatus of business data objects). Windows of GUI 390 for generating ormodifying content types are illustrated in FIGS. 5-10. Each of thefigures will be described in more detail.

FIG. 5 includes an illustration of window 50 for creating a businesscontent type. Window 50 includes tabs entitled general 500, attributes502, workflow 504, security 506, and status 508. The content typeincludes name 522 that may include a string of characters. In thisspecific example, “Article” is name 522 of the business content type.Description 524 includes a text area that can be used to describe thebusiness content type. Icon file 526 can be used to display an icon toallow for an easy instantiation of business data objects by clicking onthe icon. Default path 528 can be used to define the default path inwhich business data objects instantiated using this business contenttype will be stored.

FIG. 5 includes an extensibility section that includes content editor542, validation schema 544, and type definition 546. The extensibilitysection of the content type generation GUI provides hooks to actorcomputer 180 to customize the behavior of the content managementapplication.

Content editor 542 provides the user a place to register a page tooverride the look and feel of the default generated form and to enterthe data for a content instance object (of the specified type). The usermay have layout or look and feel requirements dictated by theirorganization and will need to override the default form.

Validation schema 544 allows the user to register an XSD file with thecontent type for server-side validation of the data entered at contentinstance creation time (usually via the generated GUI form).Verification of validation scheme 544 may be accomplished by having theuser create a pre-persistence listener to validate the object againstthe XSD. The pre-persistence listener class can be another example ofengineered extensibility in the system.

Type definition 546 can be a new class that allows the user to registera Java class with the content type object. In this manner, the new classcan inherit from a pre-existing class. The purpose of type definition546 is to provide custom logic inside of the new class yet still providethe same interface that the GUI tools use.

If the information for the business content type is acceptable, OK tile562 can be activated. Alternatively, if information for the businesscontent type is not acceptable, a business user may activate cancel tile564. In still other instances, a business user may activate apply tile566 or activate help tile 568 if the business user needs moreassistance. When the business content type is saved, the information isautomatically serialized within a structured definition expressed inXML.

FIG. 6 includes an illustration of window 60 comprising the attributesfor the article content type. The business user may specify the datasources using the tile 602. Below data source 602 includes an attributelist. A business user may add a new attribute 622, add a new data source624, move up within the list 626, move down with the list 628, or removean attribute 630.

Each of the attributes may include attribute name 640, which can be auser-friendly name that business users may change to match thevocabulary of business users or content contributors. This name does notneed to be in a form that a computer program would require to operate.Each attribute may also include XML name 642. This name will need to bein a form consistent with XML because an XML definition of the contenttype is generated using XML name 642. Therefore, the name may not haveany spaces or may be otherwise limited. The attribute may includevariable type 646. As illustrated in FIG. 6, the types include integerand character string. In another embodiment, other variable types, suchas float, double, or the like may be used. When a character string isused, length 648 may be specified. For integers, the length may not beapplicable. However, for strings, this may be nearly any finite number.In this specific example, the string lengths are either 255 characterslong or 1024 characters long.

Each attribute may include widget 650, which may also be considered acontrol. In this specific example, the article identifier will use awidget that sequentially numbers the articles. For the title andsummary, a text widget will allow a single line of text to be typed whena business data object is instantiated from this content type. The bodyincludes a text area widget. The author can be chosen using a selectwidget that can display authors using a pull-down menu. An image for thearticle may be selected using a file widget that will be used to selecta file that contains an image.

A business user can designate whether each attribute will be searchable652, whether any of the attributes will be a default label 654 for asubsequently created business data object, which attributes would bedisplayed in a summary 656 of a subsequently created business dataobject, and what portions of the information may be visible 658. More orfewer variables for each attribute may be used as desired.

A business user may click on any of the items illustrated under name640. FIGS. 7 and 8 include windows 70 and 80, respectively, for theauthor and image attributes. Referring to FIG. 7, the author can berepresented by an integer data type. Widget type 72 is currently listedas a selection list. If desired, a business user could change the widgetto a different type of widget. For example, the select list widget maybe replaced by a text widget so that name of the author could be typedby a content contributor. For a text widget, the data type may bechanged to a character string, and a limit the length of the characterstring may be input. With the select list, the business user may need toaccess a pre-existing table in a database having information of authors.If so, definition 74 and project path 76 may need to be selected.

Referring to FIG. 8, the image has a string data type and has widgettype 82 similar to widget type 72. Widget type 82 is currently set to bea file. The business user can also designate valid extensions 84 allowedfor the image files. In this specific example, valid extensions may be.jpg or .gif files. The business user may select browser root 86.Browser root 86 can be used as the default directory from which imagefiles may be selected. In this specific example, browser root 86 wouldbe within a folder entitled “SampleData.”

At this point, a business content type for an article may be generated.The article content type example is based on a referenced model. When abusiness data object is instantiated from the business content type, theobjects referenced within the business data object may or may not beprocessed together. If one of the referenced objects has already beendeployed, it will not be re-deployed when the business data object isdeployed.

FIG. 9 includes a window 90 that has a content type entitled “Product.”The prior example with an article content type used references. For theproduct content type, containment model is used. Referring to theattribute list in window 90, product identifier, product name, andproduct description may correspond to a product category. The SKUidentifier, SKU name, and SKU description may correspond to individualproducts within that product category. Additional attributes may includecolor and price. A relator widget may be used, and in FIG. 9, isillustrated the second occurrence of “PRODUCT_ID” in the attribute list.

FIG. 10 includes a window 1000 for the “PRODUCT_ID” relator widget. Thedata type is an integer, and widget type 1000 is a relator. The relatorwidget can be used for locating tuples within databases. The relatorwidget is used to manage containment within the business data object.The business user may select a database column reference as item 1022.The entries may be nested as noted by item 1042. If the entries arenested, a separate form is generated for content entry and edit. If thenested checkbox 1042 is not selected, a single form is used to createthe appearance of a monolithic object. In both cases, there is arelationship between data in multiple tables and the object uses acontainment model. Page size 1044 may be specified, and in this example,is 100. The business user may also input a minimum number of entries1046 and a maximum number of entries 1048. In this example, the numberof entries may be from 0-1000. Therefore, up to 1000 different productsmay be within this product category, and each page may display up to 100products.

Each of the individual products is contained within the productcategory. In other words, the business data object and all other datafrom persistence layer 320 that are contained or “nested” within it aretreated as a single unit. In other words, the business data object willbe processed through the workflow and deployment as a single unit.

At this point in the process, a business content type has been defined.Note that the entries, which will be defined in the business dataobject, will be contained within a product data object.

A business user can instantiate a business data object from a businesscontent type, such as the example as illustrated in FIGS. 9 and 10.Window 1100 in FIG. 11 may be displayed to a content contributor whowants to instantiate a business data object using the product contenttype. The content contributor can enter product name 1102, which in thiscase is a name of a product category. The content contributor may enterproduct description 1104. Block 1106 includes a display of the productscurrently contained within the database. Note that block 1106 includesthe SKU identifier, SKU name, SKU description, color, and price aspreviously described in FIG. 9. Products may be added, removed, oredited.

When the add or edit tablet is activated, window 1200 as illustrated inFIG. 12 may be displayed. SKU name 1202, SKU description 1204, color1222, and price 1224 may be entered or modified for each product in theproduct category. When finished, the add tablet 1242 may be activated.Otherwise, the cancel tablet 1244 may be activated.

FIG. 13 includes window 1300 for a product category of men's shoes.Window 1300 includes product name 1302, product description 1304, andfive different products within block 1322.

FIG. 14 includes window 1400 that allows for classifications of thebusiness data object being instantiated. The classification can be partof a content taxonomy. With the content taxonomy, the classificationscan be used for personalization, reporting, searching, and campaigns. Abusiness user can add classifications 1422 or remove classifications1424. Each classification may be displayed with name 1442, path 1444,and description 1446.

FIG. 15 includes an illustration of a window 1500 that is directed tochannels. Channels can belong to sites that map to some physicaltopology via a sequence of deployment groups. Content may not bedeployed unless it is assigned to one or more channels. The content canthen be deployed either directly, via the channel, or via the sitecontaining the channel (provided that the site and channel areapproved). Block 152 includes a list of channels. A business user mayadd a channel 152 or remove a channel 154.

FIG. 16 includes an illustration of window 1600 regarding versions ofthe business data object. A business user can create a new version 1622or restore a prior version 1624. Each version may include label 1642,date 1644, version number 1646, and comments 1648.

FIG. 17 includes an illustration of window 1700 that displays the statusof the business data object. The information may include approval state172, checked-out state 174, creation and modification information 176,and management identifier 178, which may be the identifier of thespecific business data object being created.

The embodiments can provide an “out-of-the-box” content managementsolution. The time to install and configure a content management systemand launch content from a network site can be reduced becauseprogrammers do not have to write code for the content types. After thesoftware is installed, the business users can start generating ormodifying content types quickly. Therefore, content contributors maystart instantiating business data objects from the content types in ashorter time period.

Part of the method and system can be achieved by using different levelsof abstraction. By creating a higher level of objects, which can be thebusiness content types, those objects can be used without needing toknow how data is managed by CMS 120. Therefore, business users mayoperate at a higher level and not have to understand the complexities ofhow content is managed by CMS 120 or even understand a programminglanguage. Business user can be work at the higher level and use namingconventions and rules that that makes sense to the business users.

Also, business content types may be generated and modified using a GUIdesigned for ease of use from the perspective of business users workingwith the content types. The GUI can be configured to let a business useradd or remove attributes and reference nearly any number of other datain different persistent data sources without knowing a programminglanguage. The attributes can have names that are more descriptive andeasier to use by the business users that will need to work with thebusiness data objects created from the business content types. Ineffect, the business user is creating a “template” without having towrite code.

Unlike templates, the content types may also include definitions forworkflow, security, status, and potentially other functions. The contenttypes can be edited using the GUI at any time. The same or otherbusiness users can use another GUI to instantiate business data objectsfrom the content types defined using the GUI.

In the foregoing specification, the invention has been described withreference to specific embodiments. However, one of ordinary skill in theart appreciates that various modifications and changes can be madewithout departing from the scope of the present invention as set forthin the claims below. Accordingly, the specification and figures are tobe regarded in an illustrative rather than a restrictive sense, and allsuch modifications are intended to be included within the scope ofpresent invention.

Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any element(s) that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeature or element of any or all the claims.

What is claimed is:
 1. A method of managing content at a network sitecomprising: generating or modifying a content type, the generating ormodifying being responsive to information provided by a user at a usercomputer using one or more entry forms presented to the user through agraphical user interface, the content type being a first level objectcontaining a structured definition; wherein: the generating or modifyingstep is performed using an application programming interface coupled tothe graphical user interface; the application programming interfaceprovides access via a first generic interface to an application serviceslayer, wherein the application services layer is configured to managethe content type; and the application services layer overlies a contentmanagement system via a second generic interface, wherein the contentmanagement system is configured for managing data in one or more datasources that are used at the network site; and instantiating a secondlevel data object from the structured definition of the content typebased on content structure desired by the user, wherein the second leveldata object utilizes the data in the one or more data sources.
 2. Themethod of claim 1, wherein the generating or modifying step is performedusing the graphical user interface that is coupled to the applicationprogramming interface.
 3. The method of claim 1, wherein the generatingor modifying step comprises specifying or editing attributes for thecontent type.
 4. The method of claim 3, wherein the generating ormodifying step comprises specifying or editing a workflow for the secondlevel data object.
 5. The method of claim 3, wherein the generating ormodifying step comprises specifying or editing an access control.
 6. Themethod of claim 3, wherein the attributes comprise an attribute nameunderstood by business users, an XML name, a variable type, and awidget.
 7. The method of claim 1, wherein dependencies of the contenttype are managed by reference, containment, or a combination thereof. 8.The method of claim 1, further comprising saving the content type,wherein saving the content type automatically serializes the informationutilizing the structured definition of the content type.
 9. Anon-transitory data processing system readable medium having codeembodied therein, the code being executable by a server computer toperform: generating or modifying a content type, the generating ormodifying being responsive to information provided by a user at a usercomputer using one or more entry forms presented to the user through agraphical user interface, the content type being a first level objectcontaining a structured definition, the graphical user interface coupledto an application programming interface providing access via a firstgeneric interface to an application services layer for managing thecontent type; and instantiating a second level data object from thestructured definition of the content type based on content structuredesired by the user, wherein the second level data object utilizes thedata in the one or more data sources, the data managed by a contentmanagement layer, the application services layer overlying the contentmanagement layer via a second generic interface.
 10. The non-transitorydata processing system readable medium of claim 9, wherein theinformation is received from the user at a different computer.
 11. Thenon-transitory data processing system readable medium of claim 9,wherein the code is further executable to perform automaticallyserializing the information.
 12. The non-transitory data processingsystem readable medium of claim 11, wherein the information isautomatically serialized within the structured definition expressed inextensible markup language (XML).
 13. The non-transitory data processingsystem readable medium of claim 9, wherein the information includes anattribute, a workflow, or an access control.
 14. The non-transitory dataprocessing system readable medium of claim 9, wherein dependencies ofthe content type are managed by reference, containment, or a combinationthereof.
 15. A system for modeling content comprising: a computerconfigured to execute a content management system application whichincludes: a content management layer, wherein the content managementlayer is configured for managing data in one or more data sources thatare used at the network site; an application services layer overlyingthe content management layer via a first generic interface, wherein theapplication services layer is configured to manage a content type, thecontent type being a first level object containing a structureddefinition; and an application programming interface providing accessvia a second generic interface to the application services layer,wherein the application programming interface is coupled to a graphicaluser interface configured to allow a user at a user computer to createor modify the content type using one or more entry forms presented tothe user through the graphical user interface, wherein the structureddefinition is sent to the content management layer via the applicationprogramming interface and application services layer, wherein a secondlevel data object is instantiated from the structured definition of thecontent type based on content structure desired by the user, wherein thesecond level data object utilizes the data in the one or more datasources.
 16. The system of claim 15, the content management systemapplication further comprising a persistence layer, wherein the contentmanagement layer overlies the persistence layer.
 17. The system of claim15, the content management system application further comprising thegraphical user interface coupled to the application programminginterface.
 18. The system of claim 17, wherein the graphical userinterface is configured to create an XML definition of the content typebased on inputs using the graphical user interface.
 19. The system ofclaim 15, the content management system application further comprising abusiness data object, wherein the business data object is aninstantiation of the content type and the content type is a businesscontent type.
 20. The system of claim 15, wherein the content typecomprises an attribute, a workflow, and an access control.
 21. Themethod according to claim 1, wherein the second level data object ispart of the content management system and references unstructuredcontent, structured content, or a combination thereof in the one or moredata sources.
 22. The non-transitory data processing system readablemedium of claim 9, wherein the second level data object is part of thecontent management layer and references unstructured content, structuredcontent, or a combination thereof in the one or more data sources. 23.The system of claim 15, wherein the second level data object is part ofthe content management layer and references unstructured content,structured content, or a combination thereof in the one or more datasources.